Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 528ed0480c6b7a92305ce0a6c16de72ad6829e9b82f96d2757c8da68d6e60b0d

Tx prefix hash: c69c57b377257dfb54b61de06cb3cec7647c761381ef2ecdb449d7a1fafd6dbe
Tx public key: b1c055efb57fc7f430d0cffcc216dea993ae7bcfa93f28e5a9fc1cf6f9fd6ce4
Timestamp: 1709781308 Timestamp [UCT]: 2024-03-07 03:15:08 Age [y:d:h:m:s]: 01:029:10:16:00
Block: 972848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282019 RingCT/type: yes/0
Extra: 01b1c055efb57fc7f430d0cffcc216dea993ae7bcfa93f28e5a9fc1cf6f9fd6ce402110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f4cc2bcf4b33537f3bcb35f700c6a7b677df477e0b1d6b76dbfa04edcecbd358 0.600000000000 1432767 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": 972858, "vin": [ { "gen": { "height": 972848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f4cc2bcf4b33537f3bcb35f700c6a7b677df477e0b1d6b76dbfa04edcecbd358" } } ], "extra": [ 1, 177, 192, 85, 239, 181, 127, 199, 244, 48, 208, 207, 252, 194, 22, 222, 169, 147, 174, 123, 207, 169, 63, 40, 229, 169, 252, 28, 246, 249, 253, 108, 228, 2, 17, 0, 0, 0, 6, 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