Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c858c05b0b83c04446717ed03892c8c9005e61a908ae1c64de8b64efa5d1a74d

Tx prefix hash: 2de619bf40b5c452f370b19dd064579673efeac56f63b582d33ae748855d5c73
Tx public key: 0cc690d215a240aca87c6f5c50a48eed927e69899b89c9275e075b0e3d57c68a
Timestamp: 1707604589 Timestamp [UCT]: 2024-02-10 22:36:29 Age [y:d:h:m:s]: 01:279:08:15:47
Block: 954785 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 458419 RingCT/type: yes/0
Extra: 010cc690d215a240aca87c6f5c50a48eed927e69899b89c9275e075b0e3d57c68a02110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 166ecd0b6a7327636f7edabee9e3d095b914ae0744637cdcd60ff46ad97f4578 0.600000000000 1414067 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": 954795, "vin": [ { "gen": { "height": 954785 } } ], "vout": [ { "amount": 600000000, "target": { "key": "166ecd0b6a7327636f7edabee9e3d095b914ae0744637cdcd60ff46ad97f4578" } } ], "extra": [ 1, 12, 198, 144, 210, 21, 162, 64, 172, 168, 124, 111, 92, 80, 164, 142, 237, 146, 126, 105, 137, 155, 137, 201, 39, 94, 7, 91, 14, 61, 87, 198, 138, 2, 17, 0, 0, 0, 8, 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