Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dee6c88d158913c212e9ad914884cc8c8ddb2d474c2ec64a02a42dee3e583b4f

Tx prefix hash: 55d79a0ae0cb6f288b595d0413898b9b49d4ddd6c6904536ded957c16e3816c6
Tx public key: 060a65a31a68d3960c7431726bc386c7e22c88ff81437adaa1114d04747d0e88
Timestamp: 1737370663 Timestamp [UCT]: 2025-01-20 10:57:43 Age [y:d:h:m:s]: 00:305:10:19:31
Block: 1201368 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215846 RingCT/type: yes/0
Extra: 01060a65a31a68d3960c7431726bc386c7e22c88ff81437adaa1114d04747d0e88021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d230a9ec1bc90865d168d8a8f4b546235c29415a908e1e24f8e9de3368c0cf9 0.600000000000 1688017 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": 1201378, "vin": [ { "gen": { "height": 1201368 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d230a9ec1bc90865d168d8a8f4b546235c29415a908e1e24f8e9de3368c0cf9" } } ], "extra": [ 1, 6, 10, 101, 163, 26, 104, 211, 150, 12, 116, 49, 114, 107, 195, 134, 199, 226, 44, 136, 255, 129, 67, 122, 218, 161, 17, 77, 4, 116, 125, 14, 136, 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