Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 779663ef596dba8bd22dbdc4b198c19c92cfc577ef79b10ebde38bb5865c2f5c

Tx prefix hash: dcac585c62d6b61931fd0708aa02f045d1b1231700da1d12db860e156931a2cb
Tx public key: 30667b2dfb05ca76fded3b0240c319c017810924c1c46a6a576dcfbaef51e957
Timestamp: 1751854664 Timestamp [UCT]: 2025-07-07 02:17:44 Age [y:d:h:m:s]: 00:137:09:40:57
Block: 1320316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96617 RingCT/type: yes/0
Extra: 0130667b2dfb05ca76fded3b0240c319c017810924c1c46a6a576dcfbaef51e9570211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 63c4524757db216cdab594f37b907126dced43d3c70e1b3c5f0ec4cce35351d6 0.600000000000 1808013 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": 1320326, "vin": [ { "gen": { "height": 1320316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "63c4524757db216cdab594f37b907126dced43d3c70e1b3c5f0ec4cce35351d6" } } ], "extra": [ 1, 48, 102, 123, 45, 251, 5, 202, 118, 253, 237, 59, 2, 64, 195, 25, 192, 23, 129, 9, 36, 193, 196, 106, 106, 87, 109, 207, 186, 239, 81, 233, 87, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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