Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a61255ba09dc668c04a898f98c3a2e3b7d32d5a9871b80515c7a55493c90a8d5

Tx prefix hash: 108138fb4bab7c74097dbc418dc149556a0daca9a5bc0f3d1ba8275cee47b345
Tx public key: 6e071179d14b11f86c36556f3d2d8e7033e7bb7f5f0137bd15ba95102507d5ee
Timestamp: 1705742687 Timestamp [UCT]: 2024-01-20 09:24:47 Age [y:d:h:m:s]: 01:072:10:53:57
Block: 939320 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 312879 RingCT/type: yes/0
Extra: 016e071179d14b11f86c36556f3d2d8e7033e7bb7f5f0137bd15ba95102507d5ee02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55ffec9361b88673ef9b3a62367f5fb37a18d39c157c43a70258d0bc69407fd2 0.600000000000 1397414 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": 939330, "vin": [ { "gen": { "height": 939320 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55ffec9361b88673ef9b3a62367f5fb37a18d39c157c43a70258d0bc69407fd2" } } ], "extra": [ 1, 110, 7, 17, 121, 209, 75, 17, 248, 108, 54, 85, 111, 61, 45, 142, 112, 51, 231, 187, 127, 95, 1, 55, 189, 21, 186, 149, 16, 37, 7, 213, 238, 2, 17, 0, 0, 0, 1, 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