Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae30d45f86be3afa5d2020c6642968f324f0e93fe0922f89df4abdb254178c32

Tx prefix hash: 5f99ec272c00bf91d147c0cc71148eaf8281709c92d2cf5aa5aa0179a3c152ca
Tx public key: 977bee501f17f3237f7fde33f585b706a77f489b56687c461c65cd5e1c617829
Timestamp: 1735037941 Timestamp [UCT]: 2024-12-24 10:59:01 Age [y:d:h:m:s]: 00:096:14:38:21
Block: 1182117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 68814 RingCT/type: yes/0
Extra: 01977bee501f17f3237f7fde33f585b706a77f489b56687c461c65cd5e1c617829021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fdc9f27d2b4f1512729aceb4698ac5d3959d0249652f0ec3e4dff0f3674b53f2 0.600000000000 1668548 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": 1182127, "vin": [ { "gen": { "height": 1182117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fdc9f27d2b4f1512729aceb4698ac5d3959d0249652f0ec3e4dff0f3674b53f2" } } ], "extra": [ 1, 151, 123, 238, 80, 31, 23, 243, 35, 127, 127, 222, 51, 245, 133, 183, 6, 167, 127, 72, 155, 86, 104, 124, 70, 28, 101, 205, 94, 28, 97, 120, 41, 2, 17, 0, 0, 0, 1, 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