Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de17f78852a51823c686430b558e8d16b8da174297cb7f005ee0135e72ee4915

Tx prefix hash: 463ac1e074e37a956fe6f6ba901aae49dd171282f0d3778a7771fc48e7ae400f
Tx public key: ce5780461c57133530e8092fdf67b18c1bf374ba9ef0a6aee689a5156bd9e8f2
Timestamp: 1727341410 Timestamp [UCT]: 2024-09-26 09:03:30 Age [y:d:h:m:s]: 00:195:16:07:44
Block: 1118418 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139660 RingCT/type: yes/0
Extra: 01ce5780461c57133530e8092fdf67b18c1bf374ba9ef0a6aee689a5156bd9e8f2021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c6ab997a826b4da89041e5e48c7b14cfd6fc8a715f24cdf43ad0f1e7eb844b9 0.600000000000 1599607 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": 1118428, "vin": [ { "gen": { "height": 1118418 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c6ab997a826b4da89041e5e48c7b14cfd6fc8a715f24cdf43ad0f1e7eb844b9" } } ], "extra": [ 1, 206, 87, 128, 70, 28, 87, 19, 53, 48, 232, 9, 47, 223, 103, 177, 140, 27, 243, 116, 186, 158, 240, 166, 174, 230, 137, 165, 21, 107, 217, 232, 242, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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