Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e52cfb24bc14d290029b285adfa9d61f5812af04043965a6149a81935061dfbb

Tx prefix hash: fe5484409237e16d7c654e76411e9aff16b2a692c7a8fe0668aeae99ca216839
Tx public key: 6f52c1318ae319bbc9b42e8f4f67819089e231e8de1e19ba92bb3ce56037b53e
Timestamp: 1708988191 Timestamp [UCT]: 2024-02-26 22:56:31 Age [y:d:h:m:s]: 01:086:22:39:29
Block: 966269 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323189 RingCT/type: yes/0
Extra: 016f52c1318ae319bbc9b42e8f4f67819089e231e8de1e19ba92bb3ce56037b53e02110000001052d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 900565724ea4f537dd51c3579f8e98c83feb3e9eebdf3b5ac057f953a54f90c2 0.600000000000 1426026 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": 966279, "vin": [ { "gen": { "height": 966269 } } ], "vout": [ { "amount": 600000000, "target": { "key": "900565724ea4f537dd51c3579f8e98c83feb3e9eebdf3b5ac057f953a54f90c2" } } ], "extra": [ 1, 111, 82, 193, 49, 138, 227, 25, 187, 201, 180, 46, 143, 79, 103, 129, 144, 137, 226, 49, 232, 222, 30, 25, 186, 146, 187, 60, 229, 96, 55, 181, 62, 2, 17, 0, 0, 0, 16, 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