Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: cd54244d81b3ef509260ab64c3d7d73cee385c1680628260524ade51ffc8daf2

Tx prefix hash: 85e7d84861e366f4fbac5be68056050d42dcd71b3266c850e4b1e70ec4003577
Tx public key: 406edf96e9edf7d9e5b7a1faf836a9d41801170bb4496d35ea1ee2299d87aec3
Timestamp: 1721493377 Timestamp [UCT]: 2024-07-20 16:36:17 Age [y:d:h:m:s]: 00:277:23:22:06
Block: 1069933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198605 RingCT/type: yes/0
Extra: 01406edf96e9edf7d9e5b7a1faf836a9d41801170bb4496d35ea1ee2299d87aec302110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8cf4e45b6b3b0dfe3126bdd7586c244c679ae149c8776de72b193b9a93f08052 0.600000000000 1541558 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1069943, "vin": [ { "gen": { "height": 1069933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8cf4e45b6b3b0dfe3126bdd7586c244c679ae149c8776de72b193b9a93f08052" } } ], "extra": [ 1, 64, 110, 223, 150, 233, 237, 247, 217, 229, 183, 161, 250, 248, 54, 169, 212, 24, 1, 23, 11, 180, 73, 109, 53, 234, 30, 226, 41, 157, 135, 174, 195, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8