Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ec8c63576b0db5678b3552b59a657cf1c743b0e7c1a1fcfba33a79543c42502c

Tx prefix hash: c26d9efacb6c6a686146fb9677a77171067201d983301bf7f48d4ed181d5d8f6
Tx public key: 895594cee974195d411ab126932f4ad42e47b352bdd11894f4ffe4809d997bdc
Timestamp: 1628481412 Timestamp [UCT]: 2021-08-09 03:56:52 Age [y:d:h:m:s]: 03:104:10:21:32
Block: 310176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 847699 RingCT/type: yes/0
Extra: 01895594cee974195d411ab126932f4ad42e47b352bdd11894f4ffe4809d997bdc021100000034a272b9cb000000000000000000

1 output(s) for total of 57.578272055000 dcy

stealth address amount amount idx
00: 944c8f29dee71508f6af5d8d40b9375f29c5f66ffe73b77727bb7620f0c0edf8 57.578272055000 645799 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": 310186, "vin": [ { "gen": { "height": 310176 } } ], "vout": [ { "amount": 57578272055, "target": { "key": "944c8f29dee71508f6af5d8d40b9375f29c5f66ffe73b77727bb7620f0c0edf8" } } ], "extra": [ 1, 137, 85, 148, 206, 233, 116, 25, 93, 65, 26, 177, 38, 147, 47, 74, 212, 46, 71, 179, 82, 189, 209, 24, 148, 244, 255, 228, 128, 157, 153, 123, 220, 2, 17, 0, 0, 0, 52, 162, 114, 185, 203, 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