Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4e9df8cb548640af540b5a6e5bc5bcc8e598ad368cd7891721c4522eb46a79

Tx prefix hash: 1ef4eb1138183c5d2fdd327fb81e3707eb97452618e49ae50f0a30ec319e5422
Tx public key: 7e7f149fefe5ae465957eef8e46cc5b412a3c914ff2e4d43ae371df960d4b42c
Timestamp: 1717299113 Timestamp [UCT]: 2024-06-02 03:31:53 Age [y:d:h:m:s]: 01:170:21:31:39
Block: 1035166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 380733 RingCT/type: yes/0
Extra: 017e7f149fefe5ae465957eef8e46cc5b412a3c914ff2e4d43ae371df960d4b42c02110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7c9e6399d5c4addbe9a2d2236ad067e8e460f20a0eca81e12a43723d2bdc8bd 0.600000000000 1503685 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": 1035176, "vin": [ { "gen": { "height": 1035166 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7c9e6399d5c4addbe9a2d2236ad067e8e460f20a0eca81e12a43723d2bdc8bd" } } ], "extra": [ 1, 126, 127, 20, 159, 239, 229, 174, 70, 89, 87, 238, 248, 228, 108, 197, 180, 18, 163, 201, 20, 255, 46, 77, 67, 174, 55, 29, 249, 96, 212, 180, 44, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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