Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba03ee6200e19495f544386327d19cfc078dffc1a5e2bd2ac57bcf2cee26699e

Tx prefix hash: 6c2bfa17cb692d5079dc601fd08fda0d539b0a98b7c9848539f37fab9dfbb0a2
Tx public key: a58d54adbc5b739fe1617917c068a7f2dc90dcbabf33ce390bc23312d9bae3d9
Timestamp: 1732774204 Timestamp [UCT]: 2024-11-28 06:10:04 Age [y:d:h:m:s]: 00:138:03:47:41
Block: 1163359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98562 RingCT/type: yes/0
Extra: 01a58d54adbc5b739fe1617917c068a7f2dc90dcbabf33ce390bc23312d9bae3d90211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 106c3e60a0f57be8c340dd737c4cfba165b622c66b058f0b565fc83ec4594b5e 0.600000000000 1649026 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": 1163369, "vin": [ { "gen": { "height": 1163359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "106c3e60a0f57be8c340dd737c4cfba165b622c66b058f0b565fc83ec4594b5e" } } ], "extra": [ 1, 165, 141, 84, 173, 188, 91, 115, 159, 225, 97, 121, 23, 192, 104, 167, 242, 220, 144, 220, 186, 191, 51, 206, 57, 11, 194, 51, 18, 217, 186, 227, 217, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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