Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa8b4ef2104f11feeb382d01986682ccae16e02c02e3822d01b9fe39f86bfd52

Tx prefix hash: 21be3f2d12b71cb897a8da9323c23403cf838461ffc2936ee81f5fe3d9f5ec09
Tx public key: c864d43db03c7ca8b1f45bcd9ad751cee1a8cfa8ce187c39f748d2ed9c3be950
Timestamp: 1656926730 Timestamp [UCT]: 2022-07-04 09:25:30 Age [y:d:h:m:s]: 02:285:17:50:07
Block: 536353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 725358 RingCT/type: yes/0
Extra: 01c864d43db03c7ca8b1f45bcd9ad751cee1a8cfa8ce187c39f748d2ed9c3be95002110000000175e3f0e9000000000000000000

1 output(s) for total of 10.252741613000 dcy

stealth address amount amount idx
00: a803e56d0088e0c840f10b2e8a13c28d7f8593f6ae12ced70faf9ab3f41f87b8 10.252741613000 966100 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": 536363, "vin": [ { "gen": { "height": 536353 } } ], "vout": [ { "amount": 10252741613, "target": { "key": "a803e56d0088e0c840f10b2e8a13c28d7f8593f6ae12ced70faf9ab3f41f87b8" } } ], "extra": [ 1, 200, 100, 212, 61, 176, 60, 124, 168, 177, 244, 91, 205, 154, 215, 81, 206, 225, 168, 207, 168, 206, 24, 124, 57, 247, 72, 210, 237, 156, 59, 233, 80, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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