Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f0003c71b5e1c4de40fa998a91433b61177c03586964a212727bffac3e1130b

Tx prefix hash: 2ed58bc02aa0af31cb6f4bd2f932881a686368037c7b9936dcb37642343cef29
Tx public key: 4fe834a9f2a3797d291dc5a8b430891c1f8b1cd9c1c2ec0cef4b2b0a377f7cf8
Timestamp: 1700642105 Timestamp [UCT]: 2023-11-22 08:35:05 Age [y:d:h:m:s]: 01:097:04:26:19
Block: 897062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330607 RingCT/type: yes/0
Extra: 014fe834a9f2a3797d291dc5a8b430891c1f8b1cd9c1c2ec0cef4b2b0a377f7cf802110000000675e3f0e9000000000000000000

1 output(s) for total of 0.654125671000 dcy

stealth address amount amount idx
00: 25f6eea5ff7393bf536a9513476f42d7059b25cee79fc28863f0738e573db221 0.654125671000 1353417 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": 897072, "vin": [ { "gen": { "height": 897062 } } ], "vout": [ { "amount": 654125671, "target": { "key": "25f6eea5ff7393bf536a9513476f42d7059b25cee79fc28863f0738e573db221" } } ], "extra": [ 1, 79, 232, 52, 169, 242, 163, 121, 125, 41, 29, 197, 168, 180, 48, 137, 28, 31, 139, 28, 217, 193, 194, 236, 12, 239, 75, 43, 10, 55, 127, 124, 248, 2, 17, 0, 0, 0, 6, 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