Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d34183c209c360f8f4b45316ab93f7fca1a959fe59bb90bffa03432619cef55

Tx prefix hash: 7802edf29b04c6484b5520a8abe21b584cb80b9a24bb49ea5eaa9c922786989e
Tx public key: 111f98ee28cf29e8b3e8b81b4d8b13157790069a728d9d5a817a7a0e4ae4542d
Timestamp: 1582433448 Timestamp [UCT]: 2020-02-23 04:50:48 Age [y:d:h:m:s]: 04:349:15:41:08
Block: 70558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1142310 RingCT/type: yes/0
Extra: 01111f98ee28cf29e8b3e8b81b4d8b13157790069a728d9d5a817a7a0e4ae4542d0211000000010aca7173000000000000000000

1 output(s) for total of 358.271992352000 dcy

stealth address amount amount idx
00: 6882c73c0bba1ca82d8df8fff3688d6f0a54527a69be9f20e00284d996b41c78 358.271992352000 130400 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": 70568, "vin": [ { "gen": { "height": 70558 } } ], "vout": [ { "amount": 358271992352, "target": { "key": "6882c73c0bba1ca82d8df8fff3688d6f0a54527a69be9f20e00284d996b41c78" } } ], "extra": [ 1, 17, 31, 152, 238, 40, 207, 41, 232, 179, 232, 184, 27, 77, 139, 19, 21, 119, 144, 6, 154, 114, 141, 157, 90, 129, 122, 122, 14, 74, 228, 84, 45, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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