Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f1e38eb1bab2e7b5e2ee19785102354955a8d18169c696db84fa111b78f6bc11

Tx prefix hash: 837e33e0f5f7522e8bc8bf864ac107a7678427ab6206ea59271ef82857078579
Tx public key: fc61cb0a7bb9d8b4aae8c99ef6c24b6347ba75b7378c2c327de4c9ab4167d9ef
Timestamp: 1695837046 Timestamp [UCT]: 2023-09-27 17:50:46 Age [y:d:h:m:s]: 01:122:10:43:05
Block: 857435 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348563 RingCT/type: yes/0
Extra: 01fc61cb0a7bb9d8b4aae8c99ef6c24b6347ba75b7378c2c327de4c9ab4167d9ef021100000007faf35c9c000000000000000000

1 output(s) for total of 0.885038070000 dcy

stealth address amount amount idx
00: ca48ad2ca0c475cb0d2e09d1423cbae761a57a4900d90c53422732883a3f14a6 0.885038070000 1311559 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": 857445, "vin": [ { "gen": { "height": 857435 } } ], "vout": [ { "amount": 885038070, "target": { "key": "ca48ad2ca0c475cb0d2e09d1423cbae761a57a4900d90c53422732883a3f14a6" } } ], "extra": [ 1, 252, 97, 203, 10, 123, 185, 216, 180, 170, 232, 201, 158, 246, 194, 75, 99, 71, 186, 117, 183, 55, 140, 44, 50, 125, 228, 201, 171, 65, 103, 217, 239, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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