Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa280f0f7c48db627e3e428044e7b70c7f9d60d913bffc7a2fde3fdbb1ac70c9

Tx prefix hash: 3169fd338132b724658b38923e912b3234fb94e87fe8a76d3608939eccf6b5ad
Tx public key: 6a38a34b706f93246884196e49a5c87ab77315c95d179c9a52e53a88bea00346
Timestamp: 1737725200 Timestamp [UCT]: 2025-01-24 13:26:40 Age [y:d:h:m:s]: 00:145:17:30:59
Block: 1204314 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103863 RingCT/type: yes/0
Extra: 016a38a34b706f93246884196e49a5c87ab77315c95d179c9a52e53a88bea003460211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fe311df964f045dff81d7de863e72db877912564348fb3bce4b0682c463217a3 0.600000000000 1690999 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": 1204324, "vin": [ { "gen": { "height": 1204314 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fe311df964f045dff81d7de863e72db877912564348fb3bce4b0682c463217a3" } } ], "extra": [ 1, 106, 56, 163, 75, 112, 111, 147, 36, 104, 132, 25, 110, 73, 165, 200, 122, 183, 115, 21, 201, 93, 23, 156, 154, 82, 229, 58, 136, 190, 160, 3, 70, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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