Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01c7fab752a9c006df8f81e034890c7fac3f6401ec1be2ea0bf4d4ed1bdeba3d

Tx prefix hash: 68ca30e3e5cb1c664807143edd785ef02b8e7d4cfb89a1d2f358fcb292b1f729
Tx public key: 636fa6be6827786401e9acc11b128c391181094e68e613aad7edee2471d46ac8
Timestamp: 1700292378 Timestamp [UCT]: 2023-11-18 07:26:18 Age [y:d:h:m:s]: 01:065:00:09:49
Block: 894166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 307825 RingCT/type: yes/0
Extra: 01636fa6be6827786401e9acc11b128c391181094e68e613aad7edee2471d46ac802110000000475e3f0e9000000000000000000

1 output(s) for total of 0.668739303000 dcy

stealth address amount amount idx
00: 5db4eb821f70be89c81401c943f059739952f8cc52781b2c10b3035a1bab6180 0.668739303000 1350357 of 0

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": 894176, "vin": [ { "gen": { "height": 894166 } } ], "vout": [ { "amount": 668739303, "target": { "key": "5db4eb821f70be89c81401c943f059739952f8cc52781b2c10b3035a1bab6180" } } ], "extra": [ 1, 99, 111, 166, 190, 104, 39, 120, 100, 1, 233, 172, 193, 27, 18, 140, 57, 17, 129, 9, 78, 104, 230, 19, 170, 215, 237, 238, 36, 113, 212, 106, 200, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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