Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e1ba559027a6f51085fa05022dba5aef1ae4a4a1b614df17ba5d13e174afc355

Tx prefix hash: 1d9d3e5e0d26558077b8fd6162935bb853616513d1aa2124974f46d1f5762aa8
Tx public key: 46f83b1de05afbb9625970eedcabfcab1c6041b38c2abf8e21967920b36fb0e4
Timestamp: 1583851468 Timestamp [UCT]: 2020-03-10 14:44:28 Age [y:d:h:m:s]: 05:061:18:44:01
Block: 79790 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1199991 RingCT/type: yes/0
Extra: 0146f83b1de05afbb9625970eedcabfcab1c6041b38c2abf8e21967920b36fb0e4021100000001c48ea382000000000000000000

1 output(s) for total of 333.905365572000 dcy

stealth address amount amount idx
00: f3fdf9cdd759fcf20e5567734ea03bde4a00b684240c871aafd5cff4e5ae5bb7 333.905365572000 146000 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": 79800, "vin": [ { "gen": { "height": 79790 } } ], "vout": [ { "amount": 333905365572, "target": { "key": "f3fdf9cdd759fcf20e5567734ea03bde4a00b684240c871aafd5cff4e5ae5bb7" } } ], "extra": [ 1, 70, 248, 59, 29, 224, 90, 251, 185, 98, 89, 112, 238, 220, 171, 252, 171, 28, 96, 65, 179, 140, 42, 191, 142, 33, 150, 121, 32, 179, 111, 176, 228, 2, 17, 0, 0, 0, 1, 196, 142, 163, 130, 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