Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d848d1f6674149f0d9758df924ed8f5649b9b0f4daf1d5c8af0e38756112ec14

Tx prefix hash: 1176b73bd70cdfa345750b45b79a7eea4435ab59a0a02ea52ef590e1d3e84fae
Tx public key: 616bf788a2e049eb12fb126578a5ba5724cd7d653e2c9867e349d7497ed65561
Timestamp: 1634669289 Timestamp [UCT]: 2021-10-19 18:48:09 Age [y:d:h:m:s]: 03:068:00:23:36
Block: 356348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 826726 RingCT/type: yes/0
Extra: 01616bf788a2e049eb12fb126578a5ba5724cd7d653e2c9867e349d7497ed6556102110000000d06faf294000000000000000000

1 output(s) for total of 40.482895105000 dcy

stealth address amount amount idx
00: e0e08df44e1ca1baefa1296bca44b69cf1f998fa6886c1aa01ce74fbdeac2b3a 40.482895105000 727106 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": 356358, "vin": [ { "gen": { "height": 356348 } } ], "vout": [ { "amount": 40482895105, "target": { "key": "e0e08df44e1ca1baefa1296bca44b69cf1f998fa6886c1aa01ce74fbdeac2b3a" } } ], "extra": [ 1, 97, 107, 247, 136, 162, 224, 73, 235, 18, 251, 18, 101, 120, 165, 186, 87, 36, 205, 125, 101, 62, 44, 152, 103, 227, 73, 215, 73, 126, 214, 85, 97, 2, 17, 0, 0, 0, 13, 6, 250, 242, 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