Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f0e9faaea043a069dd9c89a65c3089346ed9e7bc8cbbef0de184369b9722b9b2

Tx prefix hash: d0db1e94767cb3a11f8d1f3d7c996915387c4dca1fd84321ef2976470e72bbcf
Tx public key: 2c27b3c7b62cd6f9d0489ecf6570e027b5f21ac58254c2a992d978f4a9a56294
Timestamp: 1710714784 Timestamp [UCT]: 2024-03-17 22:33:04 Age [y:d:h:m:s]: 01:003:23:46:27
Block: 980597 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 263810 RingCT/type: yes/0
Extra: 012c27b3c7b62cd6f9d0489ecf6570e027b5f21ac58254c2a992d978f4a9a5629402110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 326a8d70a95071798e2d9506dd4e620837151ff3a55c638e31c7398e70fa92ce 0.600000000000 1440674 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": 980607, "vin": [ { "gen": { "height": 980597 } } ], "vout": [ { "amount": 600000000, "target": { "key": "326a8d70a95071798e2d9506dd4e620837151ff3a55c638e31c7398e70fa92ce" } } ], "extra": [ 1, 44, 39, 179, 199, 182, 44, 214, 249, 208, 72, 158, 207, 101, 112, 224, 39, 181, 242, 26, 197, 130, 84, 194, 169, 146, 217, 120, 244, 169, 165, 98, 148, 2, 17, 0, 0, 0, 7, 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