Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5639750a3fb5a20da319fd2ca5ee80b3bccda4a2344692c3c3bd81dfd58031d2

Tx prefix hash: 13e6ed66051496870c5fa282e044b0e55dde9803abc711809a001e3a616e27a6
Tx public key: 67513a3ac911e0bf099a7b5ff550b5be20ebe8f41fa7aee801a812c78afec176
Timestamp: 1735925349 Timestamp [UCT]: 2025-01-03 17:29:09 Age [y:d:h:m:s]: 00:308:03:49:24
Block: 1189462 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217733 RingCT/type: yes/0
Extra: 0167513a3ac911e0bf099a7b5ff550b5be20ebe8f41fa7aee801a812c78afec1760211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0a81a6f1636cb44479a9db3cf2fe6e99a503e4dda0656cd1ffba269ce0a91e0 0.600000000000 1675971 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": 1189472, "vin": [ { "gen": { "height": 1189462 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0a81a6f1636cb44479a9db3cf2fe6e99a503e4dda0656cd1ffba269ce0a91e0" } } ], "extra": [ 1, 103, 81, 58, 58, 201, 17, 224, 191, 9, 154, 123, 95, 245, 80, 181, 190, 32, 235, 232, 244, 31, 167, 174, 232, 1, 168, 18, 199, 138, 254, 193, 118, 2, 17, 0, 0, 0, 1, 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