Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08628aa21e7ac9e9adf29d598e70cfd313f7123b89f3bce3c419514581f65d65

Tx prefix hash: 2c57643785431116fca0d56994d9941ef540fa2af313e8e225103bfb6f74341b
Tx public key: 1f8248642d590f92788a23a66435ef9bd2a474d751a0ee834ef9dd0a080d65c9
Timestamp: 1731197917 Timestamp [UCT]: 2024-11-10 00:18:37 Age [y:d:h:m:s]: 00:131:23:26:27
Block: 1150309 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94137 RingCT/type: yes/0
Extra: 011f8248642d590f92788a23a66435ef9bd2a474d751a0ee834ef9dd0a080d65c9021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cf421a6d5bedf5ea9e19a3f7bec81ae5166e3160f5eb1dcd745be6210c1a0bb0 0.600000000000 1635582 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": 1150319, "vin": [ { "gen": { "height": 1150309 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cf421a6d5bedf5ea9e19a3f7bec81ae5166e3160f5eb1dcd745be6210c1a0bb0" } } ], "extra": [ 1, 31, 130, 72, 100, 45, 89, 15, 146, 120, 138, 35, 166, 100, 53, 239, 155, 210, 164, 116, 215, 81, 160, 238, 131, 78, 249, 221, 10, 8, 13, 101, 201, 2, 17, 0, 0, 0, 5, 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