Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b156a500056d2367ab9e52dde5c3ef4d8871d9ab5f321995eda722d0c60f41c5

Tx prefix hash: 9943925e17ae1bcd734a16c9ba853c2ca24678dcb26a64ca8cbfa337616acc19
Tx public key: b62aaac59c7ae80bf637ab14b56e9ba4902795d7a7bf8a09cb5d501d8f16bfff
Timestamp: 1730012941 Timestamp [UCT]: 2024-10-27 07:09:01 Age [y:d:h:m:s]: 00:168:05:02:27
Block: 1140533 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 120025 RingCT/type: yes/0
Extra: 01b62aaac59c7ae80bf637ab14b56e9ba4902795d7a7bf8a09cb5d501d8f16bfff021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7cd575f66d7c422cdf57c85b6060ea35881945328d1aceedde08caa5f062961 0.600000000000 1624334 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": 1140543, "vin": [ { "gen": { "height": 1140533 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7cd575f66d7c422cdf57c85b6060ea35881945328d1aceedde08caa5f062961" } } ], "extra": [ 1, 182, 42, 170, 197, 156, 122, 232, 11, 246, 55, 171, 20, 181, 110, 155, 164, 144, 39, 149, 215, 167, 191, 138, 9, 203, 93, 80, 29, 143, 22, 191, 255, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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