Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e74db10c49a839422b848f429b2a5b688e4dc3068ae6971c2ad2757d70cf1875

Tx prefix hash: 85733a3a11c53c072becce778c0556378f0aabef3b1a205d76ab81349a7a3a19
Tx public key: 2dc0fa8b7caf9101fd3634191c29d0b169f5d7bdcbed9c2afbb8de9f13a710ad
Timestamp: 1583535779 Timestamp [UCT]: 2020-03-06 23:02:59 Age [y:d:h:m:s]: 05:088:00:11:52
Block: 77754 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1218186 RingCT/type: yes/0
Extra: 012dc0fa8b7caf9101fd3634191c29d0b169f5d7bdcbed9c2afbb8de9f13a710ad02110000000dd81c26c0000000000000000000

1 output(s) for total of 339.132580126000 dcy

stealth address amount amount idx
00: 80d68d48180a198dec3a5ed6a803eeed36329ec4c9a5b1e163229f4444d4029f 339.132580126000 142945 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": 77764, "vin": [ { "gen": { "height": 77754 } } ], "vout": [ { "amount": 339132580126, "target": { "key": "80d68d48180a198dec3a5ed6a803eeed36329ec4c9a5b1e163229f4444d4029f" } } ], "extra": [ 1, 45, 192, 250, 139, 124, 175, 145, 1, 253, 54, 52, 25, 28, 41, 208, 177, 105, 245, 215, 189, 203, 237, 156, 42, 251, 184, 222, 159, 19, 167, 16, 173, 2, 17, 0, 0, 0, 13, 216, 28, 38, 192, 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