Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b82a979788816f22663097525606974186d920d4e22b038d24ff4979e6eb4ad

Tx prefix hash: 10761fcd387bd8c621dc05ca0a2725f047ff75d83b9a0a253179ecdd7960c8d7
Tx public key: d4896c2354fe62886837f42d50b2e8f9abcb2451d47e04f8e70957951ac3fc6e
Timestamp: 1705510749 Timestamp [UCT]: 2024-01-17 16:59:09 Age [y:d:h:m:s]: 01:078:22:47:38
Block: 937420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 317511 RingCT/type: yes/0
Extra: 01d4896c2354fe62886837f42d50b2e8f9abcb2451d47e04f8e70957951ac3fc6e02110000000b7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 337caaca8c142b622d89e11095cdc9dc2e5dcb65a4ccd563b6538819b6c5a93f 0.600000000000 1395474 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": 937430, "vin": [ { "gen": { "height": 937420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "337caaca8c142b622d89e11095cdc9dc2e5dcb65a4ccd563b6538819b6c5a93f" } } ], "extra": [ 1, 212, 137, 108, 35, 84, 254, 98, 136, 104, 55, 244, 45, 80, 178, 232, 249, 171, 203, 36, 81, 212, 126, 4, 248, 231, 9, 87, 149, 26, 195, 252, 110, 2, 17, 0, 0, 0, 11, 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