Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3b96db4471ed23ca3fe5b0e9811fdc44a744b0bd216e75f7f693828f055c6a4

Tx prefix hash: 3da3e66bdda6ce5237d5ada07fe70e8104cff7244888b88e502ac43e39862727
Tx public key: e9678416a906bf8b53e5ac458571d07d5b62bd5d8008c790d10e8240cadc6b21
Timestamp: 1722175681 Timestamp [UCT]: 2024-07-28 14:08:01 Age [y:d:h:m:s]: 00:094:07:27:01
Block: 1075586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67490 RingCT/type: yes/0
Extra: 01e9678416a906bf8b53e5ac458571d07d5b62bd5d8008c790d10e8240cadc6b2102110000000891e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4da5b7b6dcabeedcfddccf4ac5a2f5f4899705388c8a5e1aec33ee18664816d5 0.600000000000 1548115 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": 1075596, "vin": [ { "gen": { "height": 1075586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4da5b7b6dcabeedcfddccf4ac5a2f5f4899705388c8a5e1aec33ee18664816d5" } } ], "extra": [ 1, 233, 103, 132, 22, 169, 6, 191, 139, 83, 229, 172, 69, 133, 113, 208, 125, 91, 98, 189, 93, 128, 8, 199, 144, 209, 14, 130, 64, 202, 220, 107, 33, 2, 17, 0, 0, 0, 8, 145, 225, 60, 4, 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