Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4d9cbb81b423456a0fe9ac3bf3f4144c4239a9a436752e74c45d20fc103b8c53

Tx prefix hash: 828c61ad32a80f1e751f86e88a45ca7f088137761974b08ed6eb098cbdf78dd6
Tx public key: 7503b5565d0eea2ca24008c428d0280ac7785825089c6b7de3364b0f20ccc2a6
Timestamp: 1717330700 Timestamp [UCT]: 2024-06-02 12:18:20 Age [y:d:h:m:s]: 00:354:19:56:24
Block: 1035436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253629 RingCT/type: yes/0
Extra: 017503b5565d0eea2ca24008c428d0280ac7785825089c6b7de3364b0f20ccc2a60211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61a0cb320b87f9eb6e7ad492c31baeadd9389961af5ad1dc6c5658a543b2be8d 0.600000000000 1503957 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": 1035446, "vin": [ { "gen": { "height": 1035436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61a0cb320b87f9eb6e7ad492c31baeadd9389961af5ad1dc6c5658a543b2be8d" } } ], "extra": [ 1, 117, 3, 181, 86, 93, 14, 234, 44, 162, 64, 8, 196, 40, 208, 40, 10, 199, 120, 88, 37, 8, 156, 107, 125, 227, 54, 75, 15, 32, 204, 194, 166, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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