Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0905e86631793ac354d38803e0464d0b850f1b8d0d9c8dae1e0d56ec9d6bcea

Tx prefix hash: f88c4b1557ea21aa9d9e736045f0b37cfdd4d9250cf4835b8a3951a233be1ece
Tx public key: 5f02108fc8431f60013be5d1aaae5499d0fab55424fe7eeb4af8d48611c899e0
Timestamp: 1696420369 Timestamp [UCT]: 2023-10-04 11:52:49 Age [y:d:h:m:s]: 01:170:18:52:08
Block: 862266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383106 RingCT/type: yes/0
Extra: 015f02108fc8431f60013be5d1aaae5499d0fab55424fe7eeb4af8d48611c899e0021100000004e6d27f9c000000000000000000

1 output(s) for total of 0.853011403000 dcy

stealth address amount amount idx
00: 8ae3401854b553835979ba951b434a2d10be327b0675c8548e5f16c6c3338077 0.853011403000 1316682 of 0

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": 862276, "vin": [ { "gen": { "height": 862266 } } ], "vout": [ { "amount": 853011403, "target": { "key": "8ae3401854b553835979ba951b434a2d10be327b0675c8548e5f16c6c3338077" } } ], "extra": [ 1, 95, 2, 16, 143, 200, 67, 31, 96, 1, 59, 229, 209, 170, 174, 84, 153, 208, 250, 181, 84, 36, 254, 126, 235, 74, 248, 212, 134, 17, 200, 153, 224, 2, 17, 0, 0, 0, 4, 230, 210, 127, 156, 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