Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ffdb700ef7ab6d693d7770e5e5350c013625905107e1584aa4fdb08c22b9acd

Tx prefix hash: f8c55900971b4522043a87b92846367e28d75715b9af66f9de93681aa26638ce
Tx public key: 158d9538f12265ab491cc8bf2d5d73f9e6dbb01a3f6a226935f8e0ead141c9a4
Timestamp: 1713712400 Timestamp [UCT]: 2024-04-21 15:13:20 Age [y:d:h:m:s]: 01:029:22:12:54
Block: 1005417 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282364 RingCT/type: yes/0
Extra: 01158d9538f12265ab491cc8bf2d5d73f9e6dbb01a3f6a226935f8e0ead141c9a40211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aea584dd9977625948ff1f5e38f10231ca8dbf07f9241fe1c2e75b0910aaf3dd 0.600000000000 1466097 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": 1005427, "vin": [ { "gen": { "height": 1005417 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aea584dd9977625948ff1f5e38f10231ca8dbf07f9241fe1c2e75b0910aaf3dd" } } ], "extra": [ 1, 21, 141, 149, 56, 241, 34, 101, 171, 73, 28, 200, 191, 45, 93, 115, 249, 230, 219, 176, 26, 63, 106, 34, 105, 53, 248, 224, 234, 209, 65, 201, 164, 2, 17, 0, 0, 0, 4, 0, 17, 5, 91, 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