Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a7a4fe160452519d3d284394883ad7459367e3e84d421eb4209f34b94f86beb

Tx prefix hash: 2b1b7182e469773ca7cd7434d793a6dec85a94c81341c3fb1f9994634e58f410
Tx public key: 4ca653e90f463f3f8d3dcd94aa5091c92af0c915f90a3f997bec0289002ce743
Timestamp: 1726292371 Timestamp [UCT]: 2024-09-14 05:39:31 Age [y:d:h:m:s]: 00:162:08:58:21
Block: 1109715 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 115843 RingCT/type: yes/0
Extra: 014ca653e90f463f3f8d3dcd94aa5091c92af0c915f90a3f997bec0289002ce743021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f5751a5d0d683a4b49279b0db3fa3d83a457e2e527aa5ef327c357240cfa63d 0.600000000000 1588070 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": 1109725, "vin": [ { "gen": { "height": 1109715 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f5751a5d0d683a4b49279b0db3fa3d83a457e2e527aa5ef327c357240cfa63d" } } ], "extra": [ 1, 76, 166, 83, 233, 15, 70, 63, 63, 141, 61, 205, 148, 170, 80, 145, 201, 42, 240, 201, 21, 249, 10, 63, 153, 123, 236, 2, 137, 0, 44, 231, 67, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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