Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82a03513509bebd3faedcacca7c80f233eeba5f82391f2a07dccb44b6be31b68

Tx prefix hash: 308b9e3dffe1e70667acb556840528a36ffc3cf4b9232dbee3e854fb7e028556
Tx public key: 0fe442ad7985219ae67fd2ede50e66160c3cb8c84f42e830f29329b90020c9c4
Timestamp: 1724852596 Timestamp [UCT]: 2024-08-28 13:43:16 Age [y:d:h:m:s]: 01:071:04:43:25
Block: 1097781 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309329 RingCT/type: yes/0
Extra: 010fe442ad7985219ae67fd2ede50e66160c3cb8c84f42e830f29329b90020c9c4021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2945c62adfd4ce0e7f5146cbb40667f8e893b1739ab09dcb61fdf2aba0ae2945 0.600000000000 1573268 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": 1097791, "vin": [ { "gen": { "height": 1097781 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2945c62adfd4ce0e7f5146cbb40667f8e893b1739ab09dcb61fdf2aba0ae2945" } } ], "extra": [ 1, 15, 228, 66, 173, 121, 133, 33, 154, 230, 127, 210, 237, 229, 14, 102, 22, 12, 60, 184, 200, 79, 66, 232, 48, 242, 147, 41, 185, 0, 32, 201, 196, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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