Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc0d7cab1f10907d2828ff305ceb0015e75c87ecb5691b9d68107a2efc71b50c

Tx prefix hash: 88e23d52a165be6f8d030cb748c9ffb07e6376291b970040ef1d0b7da1132c59
Tx public key: 1c552801d4494c10510cba964d2c0e5bcfb04fc15051d238291b17bd8c57ba54
Timestamp: 1714231645 Timestamp [UCT]: 2024-04-27 15:27:25 Age [y:d:h:m:s]: 01:026:10:40:44
Block: 1009729 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279869 RingCT/type: yes/0
Extra: 011c552801d4494c10510cba964d2c0e5bcfb04fc15051d238291b17bd8c57ba5402110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25a6398059e49c941f57dc1e6f0438672d616f5ac08226c8ce8004385fbcc49d 0.600000000000 1471485 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": 1009739, "vin": [ { "gen": { "height": 1009729 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25a6398059e49c941f57dc1e6f0438672d616f5ac08226c8ce8004385fbcc49d" } } ], "extra": [ 1, 28, 85, 40, 1, 212, 73, 76, 16, 81, 12, 186, 150, 77, 44, 14, 91, 207, 176, 79, 193, 80, 81, 210, 56, 41, 27, 23, 189, 140, 87, 186, 84, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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