Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dc35b9f9265ea8eca0e045be8c3d8b1ba9c7bc03f2fb096e6c6bf68cc1705501

Tx prefix hash: 92274cd97ace3317ca5deeaa876a3a1b9cf308374fd9094809f97244db3f993f
Tx public key: c901e264647180a18dd76309eacb07003dcffa08cd959a625f4c25f625adad9c
Timestamp: 1703151398 Timestamp [UCT]: 2023-12-21 09:36:38 Age [y:d:h:m:s]: 01:324:10:04:15
Block: 917872 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 490711 RingCT/type: yes/0
Extra: 01c901e264647180a18dd76309eacb07003dcffa08cd959a625f4c25f625adad9c0211000000107a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 501e74ec9655f13b4422d19f74d38768c33853b04ce2b0db170219adb3ad12b4 0.600000000000 1375492 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": 917882, "vin": [ { "gen": { "height": 917872 } } ], "vout": [ { "amount": 600000000, "target": { "key": "501e74ec9655f13b4422d19f74d38768c33853b04ce2b0db170219adb3ad12b4" } } ], "extra": [ 1, 201, 1, 226, 100, 100, 113, 128, 161, 141, 215, 99, 9, 234, 203, 7, 0, 61, 207, 250, 8, 205, 149, 154, 98, 95, 76, 37, 246, 37, 173, 173, 156, 2, 17, 0, 0, 0, 16, 122, 156, 244, 199, 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