Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19446ffadd833c762c5184dc53cb5ae57675a162dc3b870d0aba3d711ae32356

Tx prefix hash: fd1b04309936cd621845ddd54a6d42e79b4bfaf6c3772075efccc273fda808f8
Tx public key: 428adf3c02a0d46f22e42da2ac96bea7085a9152b74294b52671bf3e844350d2
Timestamp: 1578000943 Timestamp [UCT]: 2020-01-02 21:35:43 Age [y:d:h:m:s]: 05:030:17:13:05
Block: 37439 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1171700 RingCT/type: yes/0
Extra: 01428adf3c02a0d46f22e42da2ac96bea7085a9152b74294b52671bf3e844350d2021100000037d81c26c0000000000000000000

1 output(s) for total of 461.264363145000 dcy

stealth address amount amount idx
00: 3af035a33b246ec494e0d3aa5d9eb58f0dc201dfab2e144b76dee53363771723 461.264363145000 63549 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": 37449, "vin": [ { "gen": { "height": 37439 } } ], "vout": [ { "amount": 461264363145, "target": { "key": "3af035a33b246ec494e0d3aa5d9eb58f0dc201dfab2e144b76dee53363771723" } } ], "extra": [ 1, 66, 138, 223, 60, 2, 160, 212, 111, 34, 228, 45, 162, 172, 150, 190, 167, 8, 90, 145, 82, 183, 66, 148, 181, 38, 113, 191, 62, 132, 67, 80, 210, 2, 17, 0, 0, 0, 55, 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