Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64f74d133385f5570a82d0585898f427a0cbcf09e96a8f38a06879ef0e623609

Tx prefix hash: 638962ae4a18d0163808a0617ee31c7e630773b63cce0a94817491464c0b6b9b
Tx public key: a615dd16cd5d0b3be5c827fe06be4f0a946acc305d2e5901d95a603e67e759e5
Timestamp: 1733103855 Timestamp [UCT]: 2024-12-02 01:44:15 Age [y:d:h:m:s]: 00:103:23:40:50
Block: 1166091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74132 RingCT/type: yes/0
Extra: 01a615dd16cd5d0b3be5c827fe06be4f0a946acc305d2e5901d95a603e67e759e5021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae7b3659540217461a3a8535d517a0bd49775a0df5930f2e7df10920745123bf 0.600000000000 1651768 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": 1166101, "vin": [ { "gen": { "height": 1166091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae7b3659540217461a3a8535d517a0bd49775a0df5930f2e7df10920745123bf" } } ], "extra": [ 1, 166, 21, 221, 22, 205, 93, 11, 59, 229, 200, 39, 254, 6, 190, 79, 10, 148, 106, 204, 48, 93, 46, 89, 1, 217, 90, 96, 62, 103, 231, 89, 229, 2, 17, 0, 0, 0, 4, 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