Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1d565c74931ed7ff3d1f0bfc12ff24869e24ccbbc5eb4d5329efb02e1363eaf4

Tx prefix hash: 4d206ce47bb3c4a601d58744b170fc2a65a12a49c21084e17cdeb2e698070e28
Tx public key: ee4ffd192be8fcdc4e9785cef426f92cb2399b814a76325dc6a0e0204e9499ee
Timestamp: 1716835928 Timestamp [UCT]: 2024-05-27 18:52:08 Age [y:d:h:m:s]: 00:230:07:17:26
Block: 1031341 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164807 RingCT/type: yes/0
Extra: 01ee4ffd192be8fcdc4e9785cef426f92cb2399b814a76325dc6a0e0204e9499ee02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8c1b050407858caab172e3f71fb2f21acc5d980dbf4bf6254377d48f6ba4ad5 0.600000000000 1499766 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": 1031351, "vin": [ { "gen": { "height": 1031341 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8c1b050407858caab172e3f71fb2f21acc5d980dbf4bf6254377d48f6ba4ad5" } } ], "extra": [ 1, 238, 79, 253, 25, 43, 232, 252, 220, 78, 151, 133, 206, 244, 38, 249, 44, 178, 57, 155, 129, 74, 118, 50, 93, 198, 160, 224, 32, 78, 148, 153, 238, 2, 17, 0, 0, 0, 2, 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