Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3d67f3648b30fda5f517774527045769130b9fef88b9c1c3003079c48d26265

Tx prefix hash: e24c34d46a3fc4feffc1b076962de1b4c68024c3933d1dd19365851948426fa2
Tx public key: b18596afaf3c8aa0f0042505ec8d23d9ca386b21b65b56e21825e905d6b0f314
Timestamp: 1709235543 Timestamp [UCT]: 2024-02-29 19:39:03 Age [y:d:h:m:s]: 01:024:20:51:22
Block: 968321 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 278765 RingCT/type: yes/0
Extra: 01b18596afaf3c8aa0f0042505ec8d23d9ca386b21b65b56e21825e905d6b0f31402110000001152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 298898d2f1d4b448a4241d0e900641594157058c24ef0fc7b1cace1fff37ed4a 0.600000000000 1428130 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": 968331, "vin": [ { "gen": { "height": 968321 } } ], "vout": [ { "amount": 600000000, "target": { "key": "298898d2f1d4b448a4241d0e900641594157058c24ef0fc7b1cace1fff37ed4a" } } ], "extra": [ 1, 177, 133, 150, 175, 175, 60, 138, 160, 240, 4, 37, 5, 236, 141, 35, 217, 202, 56, 107, 33, 182, 91, 86, 226, 24, 37, 233, 5, 214, 176, 243, 20, 2, 17, 0, 0, 0, 17, 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