Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3b44533581c76442ac86cc4388112d4e6f9f3c66ddccda87863ff8ba1b55958

Tx prefix hash: 720838e4d0bd9207f8136e3c1c2f530ae934f8029cd836d3bc343aade88e7666
Tx public key: 619ceb3e24396efcbb90078553aa8d9a8fc6dc0b059b056f6d0fee11778c8785
Timestamp: 1761076365 Timestamp [UCT]: 2025-10-21 19:52:45 Age [y:d:h:m:s]: 00:030:21:57:51
Block: 1394990 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 22115 RingCT/type: yes/0
Extra: 01619ceb3e24396efcbb90078553aa8d9a8fc6dc0b059b056f6d0fee11778c8785021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f39e30d574a0bc42c70f416c1eb938ca525500044bc16af8094e7d9fc0d0ec06 0.600000000000 1883265 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": 1395000, "vin": [ { "gen": { "height": 1394990 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f39e30d574a0bc42c70f416c1eb938ca525500044bc16af8094e7d9fc0d0ec06" } } ], "extra": [ 1, 97, 156, 235, 62, 36, 57, 110, 252, 187, 144, 7, 133, 83, 170, 141, 154, 143, 198, 220, 11, 5, 155, 5, 111, 109, 15, 238, 17, 119, 140, 135, 133, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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