Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 341fc2a670ad08126523f6ccfa5358975c47e6558f3a5bc48d9ca056c5b1ba29

Tx prefix hash: c5644a0d2aff0505bf94a5931559de6538e6ad5625e4f201cced6cd625b3859e
Tx public key: 34a4cbbaaea5c9fa6940dbc017308dff4bb1792d2bf453c243422f187e8f51d1
Timestamp: 1700802311 Timestamp [UCT]: 2023-11-24 05:05:11 Age [y:d:h:m:s]: 01:189:07:09:25
Block: 898390 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396517 RingCT/type: yes/0
Extra: 0134a4cbbaaea5c9fa6940dbc017308dff4bb1792d2bf453c243422f187e8f51d102110000000233af99f4000000000000000000

1 output(s) for total of 0.647531614000 dcy

stealth address amount amount idx
00: e5c6ad910301a5d392fe06774f425f281caf25452ac5ecd176b922926e611e0e 0.647531614000 1354803 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": 898400, "vin": [ { "gen": { "height": 898390 } } ], "vout": [ { "amount": 647531614, "target": { "key": "e5c6ad910301a5d392fe06774f425f281caf25452ac5ecd176b922926e611e0e" } } ], "extra": [ 1, 52, 164, 203, 186, 174, 165, 201, 250, 105, 64, 219, 192, 23, 48, 141, 255, 75, 177, 121, 45, 43, 244, 83, 194, 67, 66, 47, 24, 126, 143, 81, 209, 2, 17, 0, 0, 0, 2, 51, 175, 153, 244, 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