Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9dd8089be4cf1161805e19154f3961ab4cce84f05491f507d74724a9bf52c593

Tx prefix hash: 323ff46cef60764b95b894c9ca9ba3e44b89b57e8633e2da5c89dd27053ff294
Tx public key: f782fefefe1d15d1f1d227a3c6f0379e7739edcf4d19fe5213e085d7fbbea74e
Timestamp: 1751386724 Timestamp [UCT]: 2025-07-01 16:18:44 Age [y:d:h:m:s]: 00:142:03:03:46
Block: 1316649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99792 RingCT/type: yes/0
Extra: 01f782fefefe1d15d1f1d227a3c6f0379e7739edcf4d19fe5213e085d7fbbea74e02110000000443846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f721c9e762226832ef32b0565440bbc27fb1d9b1818a81f58b11df2f80a2d9ba 0.600000000000 1804310 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": 1316659, "vin": [ { "gen": { "height": 1316649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f721c9e762226832ef32b0565440bbc27fb1d9b1818a81f58b11df2f80a2d9ba" } } ], "extra": [ 1, 247, 130, 254, 254, 254, 29, 21, 209, 241, 210, 39, 163, 198, 240, 55, 158, 119, 57, 237, 207, 77, 25, 254, 82, 19, 224, 133, 215, 251, 190, 167, 78, 2, 17, 0, 0, 0, 4, 67, 132, 109, 102, 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