Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5e1e673f7a97568f21bb351bf1187ad5f7d10dc44578562bf40398795810561

Tx prefix hash: adc897c8c84a49a19344bd20305ec7ce5a51b00aadd2b4ddd0d7fa244ef4b847
Tx public key: e79c66119af678701a9a0ff1b7e68b2d94a37114d0cabb20f5e685fdd8e5a27c
Timestamp: 1704443222 Timestamp [UCT]: 2024-01-05 08:27:02 Age [y:d:h:m:s]: 01:096:19:17:07
Block: 928559 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330313 RingCT/type: yes/0
Extra: 01e79c66119af678701a9a0ff1b7e68b2d94a37114d0cabb20f5e685fdd8e5a27c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c7d29fd70291d6337bc673b80851b6385d263b6c4b26a949677ee5daf1ce4b4f 0.600000000000 1386419 of 15

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": 928569, "vin": [ { "gen": { "height": 928559 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c7d29fd70291d6337bc673b80851b6385d263b6c4b26a949677ee5daf1ce4b4f" } } ], "extra": [ 1, 231, 156, 102, 17, 154, 246, 120, 112, 26, 154, 15, 241, 183, 230, 139, 45, 148, 163, 113, 20, 208, 202, 187, 32, 245, 230, 133, 253, 216, 229, 162, 124, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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