Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f95abe94e67b868051bbd452f711779241f650e7a0561184d13d9a39068b4a23

Tx prefix hash: ee16166e1504cff9e7b22dc04a1f8bd7f5e6ba6f1aedd862e3a1130fc1be8dd8
Tx public key: 16cb3d3cf367c97bf8d403f429b96c365bb802e081fd5f94629279dbeb0e77eb
Timestamp: 1734504775 Timestamp [UCT]: 2024-12-18 06:52:55 Age [y:d:h:m:s]: 00:128:10:20:55
Block: 1177725 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 91566 RingCT/type: yes/0
Extra: 0116cb3d3cf367c97bf8d403f429b96c365bb802e081fd5f94629279dbeb0e77eb021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5edea21f377c6fe9171edd4c55258460917e04f5c7563a2c65f72a34d8187915 0.600000000000 1664102 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": 1177735, "vin": [ { "gen": { "height": 1177725 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5edea21f377c6fe9171edd4c55258460917e04f5c7563a2c65f72a34d8187915" } } ], "extra": [ 1, 22, 203, 61, 60, 243, 103, 201, 123, 248, 212, 3, 244, 41, 185, 108, 54, 91, 184, 2, 224, 129, 253, 95, 148, 98, 146, 121, 219, 235, 14, 119, 235, 2, 17, 0, 0, 0, 2, 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