Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1cdd98d983513c4bfe619d215ee39a7cec5b1ab518341f4d1dea90908b3ce57c

Tx prefix hash: 306da7b852a111712f7d96a66688ab548d0aea3a2d35e5555b763ee837fb9c32
Tx public key: 373db6cee63062016c19e88c92b6fd8541921e6d0adcf95513a7140768a208d1
Timestamp: 1577672464 Timestamp [UCT]: 2019-12-30 02:21:04 Age [y:d:h:m:s]: 05:110:03:09:24
Block: 34713 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1228493 RingCT/type: yes/0
Extra: 01373db6cee63062016c19e88c92b6fd8541921e6d0adcf95513a7140768a208d10211000000104ac5aa02000000000000000000

1 output(s) for total of 470.958106081000 dcy

stealth address amount amount idx
00: 4cfa4af99e06539fcb193d8d803301433533a3bf414fa28dcfd41f2313028f93 470.958106081000 58457 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": 34723, "vin": [ { "gen": { "height": 34713 } } ], "vout": [ { "amount": 470958106081, "target": { "key": "4cfa4af99e06539fcb193d8d803301433533a3bf414fa28dcfd41f2313028f93" } } ], "extra": [ 1, 55, 61, 182, 206, 230, 48, 98, 1, 108, 25, 232, 140, 146, 182, 253, 133, 65, 146, 30, 109, 10, 220, 249, 85, 19, 167, 20, 7, 104, 162, 8, 209, 2, 17, 0, 0, 0, 16, 74, 197, 170, 2, 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