Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed4467c934497cec13f659706010b25c4ad33a0d9cd1d379be5a27f3074dfce7

Tx prefix hash: 0bb5c9a1f0473c6b76c7c110a62629dcb10e23e5d9384d1f3144569977823d2a
Tx public key: 09f40f807ed47419a863feb349e31d961c95e1caaac19acc23654dd614e81ad7
Timestamp: 1706664705 Timestamp [UCT]: 2024-01-31 01:31:45 Age [y:d:h:m:s]: 01:307:11:25:16
Block: 946977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 478602 RingCT/type: yes/0
Extra: 0109f40f807ed47419a863feb349e31d961c95e1caaac19acc23654dd614e81ad702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3fd85a1c53a9be2a3448486765ac3b7a2fb7b2e8856d8795ebe47228dd3e8928 0.600000000000 1405323 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": 946987, "vin": [ { "gen": { "height": 946977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3fd85a1c53a9be2a3448486765ac3b7a2fb7b2e8856d8795ebe47228dd3e8928" } } ], "extra": [ 1, 9, 244, 15, 128, 126, 212, 116, 25, 168, 99, 254, 179, 73, 227, 29, 150, 28, 149, 225, 202, 170, 193, 154, 204, 35, 101, 77, 214, 20, 232, 26, 215, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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