Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 296afeec4c48f30423cca2ea2387b09db25509efe04b32e7ee57665d10a1cc80

Tx prefix hash: 1c84bfa7ff9645995c242b9fa8f868456922ceba2e36ec75fbbc3efc0a5f5cc6
Tx public key: 500923026adcade84cee64b813867fd6e6028ea6aa9e2254c2cda5af2a5abb0b
Timestamp: 1732904163 Timestamp [UCT]: 2024-11-29 18:16:03 Age [y:d:h:m:s]: 00:357:22:10:11
Block: 1164446 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 253334 RingCT/type: yes/0
Extra: 01500923026adcade84cee64b813867fd6e6028ea6aa9e2254c2cda5af2a5abb0b021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5788e98daefbf27f49b4a85a518cb4ff58dd4302e8a8a734d880e256eba0df02 0.600000000000 1650119 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": 1164456, "vin": [ { "gen": { "height": 1164446 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5788e98daefbf27f49b4a85a518cb4ff58dd4302e8a8a734d880e256eba0df02" } } ], "extra": [ 1, 80, 9, 35, 2, 106, 220, 173, 232, 76, 238, 100, 184, 19, 134, 127, 214, 230, 2, 142, 166, 170, 158, 34, 84, 194, 205, 165, 175, 42, 90, 187, 11, 2, 17, 0, 0, 0, 3, 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