Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f343a339f1857509045c39097297a6b3c92da45b70db551fee41eaf7a7771ec

Tx prefix hash: 97fee6531f53499480adde116dbc3cc14b06b0f5df34a0217ca3ce1a6b63b0c9
Tx public key: 1152ac14878ead35e416465fe7145fbbc2a2ddbf8d3d3d41362f47caa3ca40f2
Timestamp: 1706504186 Timestamp [UCT]: 2024-01-29 04:56:26 Age [y:d:h:m:s]: 01:138:06:41:18
Block: 945647 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359860 RingCT/type: yes/0
Extra: 011152ac14878ead35e416465fe7145fbbc2a2ddbf8d3d3d41362f47caa3ca40f202110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bca588d1ac7362b1d6415c75069d64e9a0d9e236c971f8bd67053891467a904a 0.600000000000 1403963 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": 945657, "vin": [ { "gen": { "height": 945647 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bca588d1ac7362b1d6415c75069d64e9a0d9e236c971f8bd67053891467a904a" } } ], "extra": [ 1, 17, 82, 172, 20, 135, 142, 173, 53, 228, 22, 70, 95, 231, 20, 95, 187, 194, 162, 221, 191, 141, 61, 61, 65, 54, 47, 71, 202, 163, 202, 64, 242, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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