Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91b7bfbe8b26c29437796c9932c06ff2273ce4133f2cf0abf91503f473c0e7a3

Tx prefix hash: b9b24078f8a19ec727c2d15ca92fb4772a228f52c8d353ed6af52ba7ecfb60e6
Tx public key: e5d3a1e0ce13d6c1e79dc1fe54c4d84695716ae73dff043fa3d6016f80268152
Timestamp: 1574665945 Timestamp [UCT]: 2019-11-25 07:12:25 Age [y:d:h:m:s]: 05:186:23:35:39
Block: 16998 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1276319 RingCT/type: yes/0
Extra: 01e5d3a1e0ce13d6c1e79dc1fe54c4d84695716ae73dff043fa3d6016f80268152021100000002354bbe3b000000000000000000

1 output(s) for total of 539.112561341000 dcy

stealth address amount amount idx
00: fe450037f765e41fa438a6cfaa96a7e3db2deed196e70848c677f86a9b801ef3 539.112561341000 24265 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": 17008, "vin": [ { "gen": { "height": 16998 } } ], "vout": [ { "amount": 539112561341, "target": { "key": "fe450037f765e41fa438a6cfaa96a7e3db2deed196e70848c677f86a9b801ef3" } } ], "extra": [ 1, 229, 211, 161, 224, 206, 19, 214, 193, 231, 157, 193, 254, 84, 196, 216, 70, 149, 113, 106, 231, 61, 255, 4, 63, 163, 214, 1, 111, 128, 38, 129, 82, 2, 17, 0, 0, 0, 2, 53, 75, 190, 59, 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