Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11f5d256a61b42ad0245c7b8815ae46abe7dd85c2c66884d938e4b518576d29b

Tx prefix hash: e360198686560dea4ea41e8e46b1e7436a0f369cc9ef214f373a936600401d6d
Tx public key: a1bbf402afa259e894132217f6f7eb80ac31b22c7fde230c878293bbeff4754c
Timestamp: 1711262969 Timestamp [UCT]: 2024-03-24 06:49:29 Age [y:d:h:m:s]: 01:052:10:19:12
Block: 985141 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 298448 RingCT/type: yes/0
Extra: 01a1bbf402afa259e894132217f6f7eb80ac31b22c7fde230c878293bbeff4754c02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f0d314c5f65c3a5e527e46eb8ddb374214ebeffd91b298c0e2f17a089ea030d 0.600000000000 1445348 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": 985151, "vin": [ { "gen": { "height": 985141 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f0d314c5f65c3a5e527e46eb8ddb374214ebeffd91b298c0e2f17a089ea030d" } } ], "extra": [ 1, 161, 187, 244, 2, 175, 162, 89, 232, 148, 19, 34, 23, 246, 247, 235, 128, 172, 49, 178, 44, 127, 222, 35, 12, 135, 130, 147, 187, 239, 244, 117, 76, 2, 17, 0, 0, 0, 3, 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