Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ad71ff2a76ec9c95e1e476ec6ce703dc7a5cfdda922bda279d16f9ab5c4bf14

Tx prefix hash: b25bf07514fac0a58fa53cd9e96fc85de281120baa611b78c3a91e746e138585
Tx public key: f92896dc939d957c5544f039336c411b4293d5deded21195f6883c51576f6f29
Timestamp: 1761912950 Timestamp [UCT]: 2025-10-31 12:15:50 Age [y:d:h:m:s]: 00:008:14:33:53
Block: 1401921 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 6151 RingCT/type: yes/0
Extra: 01f92896dc939d957c5544f039336c411b4293d5deded21195f6883c51576f6f290211000000025dfbbe2a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 227502f35a2f3cfcb1e487daaf39a9e681e6f2fcfad4b6e4f7f902751ced8eef 0.600000000000 1890240 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": 1401931, "vin": [ { "gen": { "height": 1401921 } } ], "vout": [ { "amount": 600000000, "target": { "key": "227502f35a2f3cfcb1e487daaf39a9e681e6f2fcfad4b6e4f7f902751ced8eef" } } ], "extra": [ 1, 249, 40, 150, 220, 147, 157, 149, 124, 85, 68, 240, 57, 51, 108, 65, 27, 66, 147, 213, 222, 222, 210, 17, 149, 246, 136, 60, 81, 87, 111, 111, 41, 2, 17, 0, 0, 0, 2, 93, 251, 190, 42, 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