Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8125ca59ea1cf5173ee0087ed177cd5c2c5c44b34a3fc46f91de9a69670b62f9

Tx prefix hash: f443d79ede837b124036694c2fcdcd5be65f252d64206d7f857f3e5f09365d3e
Tx public key: 35953634636d12e053b9b832f122abd231cafe40089947df036cefc20d4b1e34
Timestamp: 1580885800 Timestamp [UCT]: 2020-02-05 06:56:40 Age [y:d:h:m:s]: 04:363:05:58:57
Block: 58837 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1150950 RingCT/type: yes/0
Extra: 0135953634636d12e053b9b832f122abd231cafe40089947df036cefc20d4b1e34021100000002391a8d0e000000000000000000

1 output(s) for total of 391.786452583000 dcy

stealth address amount amount idx
00: e3c6f42e0f0c44e81975cfc13e9892bc1c4ee3adc821874c60a2da269a8e1bc6 391.786452583000 108749 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": 58847, "vin": [ { "gen": { "height": 58837 } } ], "vout": [ { "amount": 391786452583, "target": { "key": "e3c6f42e0f0c44e81975cfc13e9892bc1c4ee3adc821874c60a2da269a8e1bc6" } } ], "extra": [ 1, 53, 149, 54, 52, 99, 109, 18, 224, 83, 185, 184, 50, 241, 34, 171, 210, 49, 202, 254, 64, 8, 153, 71, 223, 3, 108, 239, 194, 13, 75, 30, 52, 2, 17, 0, 0, 0, 2, 57, 26, 141, 14, 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