Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3746adac61f62d9aa0d7745301d08d505556c78f860938448dcb86ef3bc7d0bd

Tx prefix hash: 405540e94b388de21875595e371231de1ce0bf85d7c4923c8bf7f395a310e1d9
Tx public key: bf4f03692a239ce455673abf44940ba8a9a85fb65c013e5d4c8824254c50b284
Timestamp: 1724114394 Timestamp [UCT]: 2024-08-20 00:39:54 Age [y:d:h:m:s]: 00:296:13:18:22
Block: 1091676 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211813 RingCT/type: yes/0
Extra: 01bf4f03692a239ce455673abf44940ba8a9a85fb65c013e5d4c8824254c50b28402110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 76fe5e4134adbb7af77737133b431c42e198072cbb4a6b545e09dbf7e145f199 0.600000000000 1566309 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": 1091686, "vin": [ { "gen": { "height": 1091676 } } ], "vout": [ { "amount": 600000000, "target": { "key": "76fe5e4134adbb7af77737133b431c42e198072cbb4a6b545e09dbf7e145f199" } } ], "extra": [ 1, 191, 79, 3, 105, 42, 35, 156, 228, 85, 103, 58, 191, 68, 148, 11, 168, 169, 168, 95, 182, 92, 1, 62, 93, 76, 136, 36, 37, 76, 80, 178, 132, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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