Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af5a7a6916b7497d2f665a1c96225c8ef750eb667e52e593f57ff2f4093a5486

Tx prefix hash: f1ffd05a9dbf7a86d519ca3e7767d424995a667415a22d8b2fda287514068ca3
Tx public key: 6dd3d1e7e44ccc4f197aa783632b0a080d292a23eca34dd20d81cba580f991fc
Timestamp: 1737398367 Timestamp [UCT]: 2025-01-20 18:39:27 Age [y:d:h:m:s]: 00:294:10:43:32
Block: 1201603 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 207970 RingCT/type: yes/0
Extra: 016dd3d1e7e44ccc4f197aa783632b0a080d292a23eca34dd20d81cba580f991fc0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 24570768bc5ed63a38e9e3699925296869164e5dd695c6f31b061fe786e4a4cc 0.600000000000 1688256 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": 1201613, "vin": [ { "gen": { "height": 1201603 } } ], "vout": [ { "amount": 600000000, "target": { "key": "24570768bc5ed63a38e9e3699925296869164e5dd695c6f31b061fe786e4a4cc" } } ], "extra": [ 1, 109, 211, 209, 231, 228, 76, 204, 79, 25, 122, 167, 131, 99, 43, 10, 8, 13, 41, 42, 35, 236, 163, 77, 210, 13, 129, 203, 165, 128, 249, 145, 252, 2, 17, 0, 0, 0, 5, 31, 10, 83, 235, 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