Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e38ac019de104ebcc2202effaa5d9d6b54327215c13f4fa4cd413b660f239d0e

Tx prefix hash: 18c5d38b0f8ec6948482f137078145013647e7992a4c1198934d27a8111cea9a
Tx public key: c437241884b80ead8a1124a2a975bc6bab64346dc0a0bc39685ed50a8b9fc2f0
Timestamp: 1737095587 Timestamp [UCT]: 2025-01-17 06:33:07 Age [y:d:h:m:s]: 00:153:10:15:22
Block: 1199136 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109356 RingCT/type: yes/0
Extra: 01c437241884b80ead8a1124a2a975bc6bab64346dc0a0bc39685ed50a8b9fc2f0021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 403ea2e4b528b3f039d6356a891954f0fdf26e60f93c8e0fa61d1517049cfa7c 0.600000000000 1685765 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": 1199146, "vin": [ { "gen": { "height": 1199136 } } ], "vout": [ { "amount": 600000000, "target": { "key": "403ea2e4b528b3f039d6356a891954f0fdf26e60f93c8e0fa61d1517049cfa7c" } } ], "extra": [ 1, 196, 55, 36, 24, 132, 184, 14, 173, 138, 17, 36, 162, 169, 117, 188, 107, 171, 100, 52, 109, 192, 160, 188, 57, 104, 94, 213, 10, 139, 159, 194, 240, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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