Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d01b8235f21e272f3cf0d6488f1303e0622d90d994567fa466ef108d03dcd3be

Tx prefix hash: ccc3b4712c5cd36a645556c150d24b4a58159553a8dd748f3e2b0c9756a7a6c8
Tx public key: 64918e88b49c62fcefa106b00ed97a4749d178fb25208c1f386790e1cf0af7e3
Timestamp: 1702786746 Timestamp [UCT]: 2023-12-17 04:19:06 Age [y:d:h:m:s]: 01:327:03:38:34
Block: 914847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 492669 RingCT/type: yes/0
Extra: 0164918e88b49c62fcefa106b00ed97a4749d178fb25208c1f386790e1cf0af7e302110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3dd6ef0be1de79ac9d473f999a59a552f91c9af4e287fd398b5f4f3de8f74a72 0.600000000000 1372199 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": 914857, "vin": [ { "gen": { "height": 914847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3dd6ef0be1de79ac9d473f999a59a552f91c9af4e287fd398b5f4f3de8f74a72" } } ], "extra": [ 1, 100, 145, 142, 136, 180, 156, 98, 252, 239, 161, 6, 176, 14, 217, 122, 71, 73, 209, 120, 251, 37, 32, 140, 31, 56, 103, 144, 225, 207, 10, 247, 227, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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