Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 020dd935359d7cee25aadddf48b24fb34de5ca073ce888f4dc52fa972b1a1605

Tx prefix hash: dbd46c4fef6a9f5264aecb666e9faf8e59de67a41539ec7f6163f82ee01d30da
Tx public key: 249a3526ffb36051aa2875e68eb97c154f1f7e8be4dab5e94e96a192d6bfaef8
Timestamp: 1717162849 Timestamp [UCT]: 2024-05-31 13:40:49 Age [y:d:h:m:s]: 00:335:15:50:46
Block: 1034040 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 239901 RingCT/type: yes/0
Extra: 01249a3526ffb36051aa2875e68eb97c154f1f7e8be4dab5e94e96a192d6bfaef80211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71c930fe0aacdc29d81e95bc10126ce2e4485dd44da01817d671ddc2b92d905b 0.600000000000 1502513 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": 1034050, "vin": [ { "gen": { "height": 1034040 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71c930fe0aacdc29d81e95bc10126ce2e4485dd44da01817d671ddc2b92d905b" } } ], "extra": [ 1, 36, 154, 53, 38, 255, 179, 96, 81, 170, 40, 117, 230, 142, 185, 124, 21, 79, 31, 126, 139, 228, 218, 181, 233, 78, 150, 161, 146, 214, 191, 174, 248, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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