Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca54d2b6df16980e8f44ab7a3294c796bf869cacfbe11b68eb5708539142ae50

Tx prefix hash: 7bc7329f630765d8276a4b5548544597dee3ebf093014399af5fca8de8cea62c
Tx public key: 50ab3cbb59d4b96f1f42bb271c3304137dab89b1f6c7ad0311bbb4e1cbe03329
Timestamp: 1712768965 Timestamp [UCT]: 2024-04-10 17:09:25 Age [y:d:h:m:s]: 00:199:02:32:24
Block: 997579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142626 RingCT/type: yes/0
Extra: 0150ab3cbb59d4b96f1f42bb271c3304137dab89b1f6c7ad0311bbb4e1cbe033290211000000067a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae2f0980ff4afb2ef1dc87baa555da40c320e03d9d0a89299b43b0b96e2b81d3 0.600000000000 1458013 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": 997589, "vin": [ { "gen": { "height": 997579 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae2f0980ff4afb2ef1dc87baa555da40c320e03d9d0a89299b43b0b96e2b81d3" } } ], "extra": [ 1, 80, 171, 60, 187, 89, 212, 185, 111, 31, 66, 187, 39, 28, 51, 4, 19, 125, 171, 137, 177, 246, 199, 173, 3, 17, 187, 180, 225, 203, 224, 51, 41, 2, 17, 0, 0, 0, 6, 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