Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 50b57bec0f926ce0143fcc3f9264aff8f9ffc3e947e8d0a3aaaf92e18d108efc

Tx prefix hash: d0117ae17ed42140ea17489f4799ea294823924ceb4d63e24d09e6e709aabdc0
Tx public key: 9f1fb2c3c09e43165724952981fa1a506b7b6b124a13f2b72549852db653a11d
Timestamp: 1715231823 Timestamp [UCT]: 2024-05-09 05:17:03 Age [y:d:h:m:s]: 00:328:20:56:32
Block: 1018026 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 235066 RingCT/type: yes/0
Extra: 019f1fb2c3c09e43165724952981fa1a506b7b6b124a13f2b72549852db653a11d02110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 553c120caa4209b6070278cf192d54ad3c40849ef1d72d86ed16001b7d688fb0 0.600000000000 1481811 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": 1018036, "vin": [ { "gen": { "height": 1018026 } } ], "vout": [ { "amount": 600000000, "target": { "key": "553c120caa4209b6070278cf192d54ad3c40849ef1d72d86ed16001b7d688fb0" } } ], "extra": [ 1, 159, 31, 178, 195, 192, 158, 67, 22, 87, 36, 149, 41, 129, 250, 26, 80, 107, 123, 107, 18, 74, 19, 242, 183, 37, 73, 133, 45, 182, 83, 161, 29, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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