Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 989fe054e0071f420259ca4facb2fd067cb6f625582a67ed5c69236b2d76a977

Tx prefix hash: e1d62aa7ff5725fcc88c160ea73f0f28317daf42a35920cfa778dbe248eeec9a
Tx public key: a8a8abe69cb13a879150aa539b3d5c2bd8f7744b6bd7b2154bf59601989e4030
Timestamp: 1736128980 Timestamp [UCT]: 2025-01-06 02:03:00 Age [y:d:h:m:s]: 00:101:09:51:44
Block: 1191144 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72258 RingCT/type: yes/0
Extra: 01a8a8abe69cb13a879150aa539b3d5c2bd8f7744b6bd7b2154bf59601989e403002110000000c1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f65da84103e479d76adf2d302d18abd2eb94afa8c42b6f27a91749fd92345b4d 0.600000000000 1677667 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": 1191154, "vin": [ { "gen": { "height": 1191144 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f65da84103e479d76adf2d302d18abd2eb94afa8c42b6f27a91749fd92345b4d" } } ], "extra": [ 1, 168, 168, 171, 230, 156, 177, 58, 135, 145, 80, 170, 83, 155, 61, 92, 43, 216, 247, 116, 75, 107, 215, 178, 21, 75, 245, 150, 1, 152, 158, 64, 48, 2, 17, 0, 0, 0, 12, 31, 10, 83, 235, 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