Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e5123a2257dfdf26f5a0f85fe681eeb87a04d80079d91e8101993380bcc8a62e

Tx prefix hash: 7a5a9f9711a3da71d911cba6cab426b29ae03d7c39d2b9a8d96417f614132b01
Tx public key: 28f062feea88e0fdc862810e94e502996aaeaba332d30c5b7448f78b50ee399a
Timestamp: 1574650205 Timestamp [UCT]: 2019-11-25 02:50:05 Age [y:d:h:m:s]: 05:158:17:22:48
Block: 16839 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1256106 RingCT/type: yes/0
Extra: 0128f062feea88e0fdc862810e94e502996aaeaba332d30c5b7448f78b50ee399a021100000001f95225a5000000000000000000

1 output(s) for total of 539.766943950000 dcy

stealth address amount amount idx
00: 95a457e830e95b77c2394f9215c05dd1d2ff031e0780fe62208e0ec9d863e678 539.766943950000 23901 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": 16849, "vin": [ { "gen": { "height": 16839 } } ], "vout": [ { "amount": 539766943950, "target": { "key": "95a457e830e95b77c2394f9215c05dd1d2ff031e0780fe62208e0ec9d863e678" } } ], "extra": [ 1, 40, 240, 98, 254, 234, 136, 224, 253, 200, 98, 129, 14, 148, 229, 2, 153, 106, 174, 171, 163, 50, 211, 12, 91, 116, 72, 247, 139, 80, 238, 57, 154, 2, 17, 0, 0, 0, 1, 249, 82, 37, 165, 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