Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b3da34d7b54370e780a262758a92f68fe60f678a73df1873584a464258a28edb

Tx prefix hash: 1e3c615144737583c037f5f8842f53fa6b1d22e3c33e19eddf2dd9539c26c350
Tx public key: a9cb2a0a563f0abd56b006fa7bd8dfd5bc71634d966b4eeede772a3ec8331086
Timestamp: 1582424214 Timestamp [UCT]: 2020-02-23 02:16:54 Age [y:d:h:m:s]: 04:311:05:42:21
Block: 70479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1115106 RingCT/type: yes/0
Extra: 01a9cb2a0a563f0abd56b006fa7bd8dfd5bc71634d966b4eeede772a3ec83310860211000000118a2ee0d9000000000000000000

1 output(s) for total of 358.506566736000 dcy

stealth address amount amount idx
00: 42c7bb5f51d3e674d387eff337dcc55024bfdfc14cf4eabd85ce585ca2025366 358.506566736000 130255 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": 70489, "vin": [ { "gen": { "height": 70479 } } ], "vout": [ { "amount": 358506566736, "target": { "key": "42c7bb5f51d3e674d387eff337dcc55024bfdfc14cf4eabd85ce585ca2025366" } } ], "extra": [ 1, 169, 203, 42, 10, 86, 63, 10, 189, 86, 176, 6, 250, 123, 216, 223, 213, 188, 113, 99, 77, 150, 107, 78, 238, 222, 119, 42, 62, 200, 51, 16, 134, 2, 17, 0, 0, 0, 17, 138, 46, 224, 217, 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