Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32859b702a45e1d3a08cbab3fae55104fd8f7055633888eda24f431181353171

Tx prefix hash: b0a7a7438b7aca314fa299b9416b442dfeb6dd7062149ab0312f865554f7a46a
Tx public key: 7ae446e957d40d2dfe170f518b4e10a08b9c8edb6b48d647dbca825e0b23e26e
Timestamp: 1722640580 Timestamp [UCT]: 2024-08-02 23:16:20 Age [y:d:h:m:s]: 00:174:22:09:07
Block: 1079442 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 125097 RingCT/type: yes/0
Extra: 017ae446e957d40d2dfe170f518b4e10a08b9c8edb6b48d647dbca825e0b23e26e021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80560ca57cee03158e5dfcb8a845af3224c3f3875998a4248bd48be9dfaecfdc 0.600000000000 1552397 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": 1079452, "vin": [ { "gen": { "height": 1079442 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80560ca57cee03158e5dfcb8a845af3224c3f3875998a4248bd48be9dfaecfdc" } } ], "extra": [ 1, 122, 228, 70, 233, 87, 212, 13, 45, 254, 23, 15, 81, 139, 78, 16, 160, 139, 156, 142, 219, 107, 72, 214, 71, 219, 202, 130, 94, 11, 35, 226, 110, 2, 17, 0, 0, 0, 3, 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