Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74d04dd6e5a5f02d669f66513c245fdd602ea46ba1c86b55d570e120beebfdb5

Tx prefix hash: 558ab3722b8c94aa9fba71d0c33f11fb10a93db40911fda88773d185f8115d1d
Tx public key: 5ffea9f6df2260bce893b799a35cdfc8ef204070224b0ef26c95d2d2664de848
Timestamp: 1759591000 Timestamp [UCT]: 2025-10-04 15:16:40 Age [y:d:h:m:s]: 00:036:04:24:13
Block: 1382671 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 25912 RingCT/type: yes/0
Extra: 015ffea9f6df2260bce893b799a35cdfc8ef204070224b0ef26c95d2d2664de848021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6dbdaf8535981e1056f1686d0bf66ebbb953d78e51fbb3b93ea733742b4c49f6 0.600000000000 1870806 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": 1382681, "vin": [ { "gen": { "height": 1382671 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6dbdaf8535981e1056f1686d0bf66ebbb953d78e51fbb3b93ea733742b4c49f6" } } ], "extra": [ 1, 95, 254, 169, 246, 223, 34, 96, 188, 232, 147, 183, 153, 163, 92, 223, 200, 239, 32, 64, 112, 34, 75, 14, 242, 108, 149, 210, 210, 102, 77, 232, 72, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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