Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: efa713ef596063eda2baa88d044d9b6e5e6774bbd0f2f047bc33f62349e31aac

Tx prefix hash: 518422d78c9d40b79e1ba2a5b95ac1c25805c665ff54bd671bc43684fca3e455
Tx public key: 64caa344c6e474f43b066cba33158627e4266b5b1f2c70f9f868d4d63cca6c5c
Timestamp: 1720209118 Timestamp [UCT]: 2024-07-05 19:51:58 Age [y:d:h:m:s]: 00:314:02:18:32
Block: 1059278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224456 RingCT/type: yes/0
Extra: 0164caa344c6e474f43b066cba33158627e4266b5b1f2c70f9f868d4d63cca6c5c0211000000015ff1157f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7669beab2b36cc28bf82d0bde73a28143a7ed31f3bc8171cf867edf4ec8d97e0 0.600000000000 1529745 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": 1059288, "vin": [ { "gen": { "height": 1059278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7669beab2b36cc28bf82d0bde73a28143a7ed31f3bc8171cf867edf4ec8d97e0" } } ], "extra": [ 1, 100, 202, 163, 68, 198, 228, 116, 244, 59, 6, 108, 186, 51, 21, 134, 39, 228, 38, 107, 91, 31, 44, 112, 249, 248, 104, 212, 214, 60, 202, 108, 92, 2, 17, 0, 0, 0, 1, 95, 241, 21, 127, 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