Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0287ccbf2712a55f33a617d506d0da0d4ff2625087d8bfff4317fbdce264a8f3

Tx prefix hash: 045421eb474bfd57a09fb18f35064c2f4f99abb2c742259d61066b31596e2c56
Tx public key: 1ed7f660852c17febd88b8a52ac9b4e9d25d81cc65a46c83b9bd35e36f61f277
Timestamp: 1718019312 Timestamp [UCT]: 2024-06-10 11:35:12 Age [y:d:h:m:s]: 01:149:10:26:52
Block: 1041139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 365358 RingCT/type: yes/0
Extra: 011ed7f660852c17febd88b8a52ac9b4e9d25d81cc65a46c83b9bd35e36f61f27702110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4113d21509270500dfe7a39df59951998c71afc308c383d91ea3132ab826c23d 0.600000000000 1509804 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": 1041149, "vin": [ { "gen": { "height": 1041139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4113d21509270500dfe7a39df59951998c71afc308c383d91ea3132ab826c23d" } } ], "extra": [ 1, 30, 215, 246, 96, 133, 44, 23, 254, 189, 136, 184, 165, 42, 201, 180, 233, 210, 93, 129, 204, 101, 164, 108, 131, 185, 189, 53, 227, 111, 97, 242, 119, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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